Meet with Scott Gunn

23-02-08 Meet with Scott Gunn.txt

Discussion: STRY0060370 - FSM_Table Fields: Work Order/Customer Information New

	var gr = new GlideRecord;
	gr.addQuery('blah', blah);
	gr.query();

MAIN ISSUE: its much easier to implement CI V4.0 intake mechanism using preexisting variable set than it is on Task table(s).

For a non-catalog item (no variable sets), the requirement for STRY0060370 involves:

  • Custom building the same functionality found in variable sets into standard client scripts and UI policies. with..flexible, client-callable (GlideAjax) centralized script.
  • Decision: whether to (A) create scripts and policies on [Task] that launch on every task type, then filter & bail, or (B) create matching scripts and policies on [..extended tables], which call the centralized script.
  • Scope: since all task types cannot be tested, stated scope is required, likely (Work Order, Incident). - Any larger scope would cause delays by colliding with other developers.

Scott thinks the scope needs refinement and is worried about workload of inventing/testing this functionality for Task.

TO-DO: ( Combined wth list from 2/02 )

  • Mhz:
    • need to get all the Checklist step text's concatenated into the import set table, procedureText field.
    • need to ensure that Checklist query reflects what Wizard Software said re: individual steps can related to other assets.
    • Need Asset import into new Servicenow data source, specify.
    • Talk to Mark & Ryan about the GlideAjax / Script Include implementation for WO (Inc?) and whether Thirdera project/scope/SOW cost is viable for that? (Or our Me/guys?) UPDATE: Scott thinks it would work in workspace.
  • Scott:
    • saw the WO0010207 (lluhdev1b) and realizes that my RP of "" shows the Task fields to populate.
    • he will work on displaying those on the WO form, and said he will revisit adding client scripts on WO form to create Customer Info V4.0 experience